-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rustdoc: Use correct def_id for doctree::Import #79751
Conversation
abad34a
to
c254a15
Compare
@bors r+ I have a nagging feeling this is fixing the symptom instead of the underlying bug, since the JSON module is still getting tricked into overwriting the original item with the import, but this seems strictly better than the current ICE so I'm ok with merging it for now. |
📌 Commit c254a15 has been approved by |
⌛ Testing commit c254a15 with merge 34aaff8c6343edf57d1716b9119e3e11770da033... |
💔 Test failed - checks-actions |
Cargotest failed while testing xsv because proptest's test cases are randomized. cc @rust-lang/infra - I thought we got rid of randomized tests at some point? Did we miss some? cc @BurntSushi, you may be interested in fixing the xsv bug (assuming it hasn't already been fixed on master, I think cargotest is pretty out of date): https://github.com/rust-lang-ci/rust/runs/1511131529#step:24:8300 @bors retry |
@jyn514 I think that bug (or test) should be fixed on master. Are y'all using master or the latest release? The latest release is pretty old at this point and I'm not sure when I'll get the next one out. |
We appear to be using a pinned commit from 2017 🤦 rust/src/tools/cargotest/main.rs Line 39 in b5ff9c3
I'll see about updating that. |
Theres 2 things going on here, that caused 2 items with the same ID to be inserted, only one of which this fixes
I've added a check that the item removed from the map is the same as what was put, so we ICE if case 1 comes back. For now, case 2 is silently ignored, but this will be changed when it is fixed. |
Well, but they're being given the ID of the item, right, not the id of the import? I think that's where the duplicates come from, it's being stored for both the import and the original item. Consider
Right now I think it will insert |
☀️ Test successful - checks-actions |
Update xsv to prevent random CI failures This fixes occasional proptest failures due to a bug in xsv, which aren't related to bugs in the rust compiler. See rust-lang#79751 (comment) for context.
@rustbot modify labels +A-rustdoc-json |
The default overwrites the crate root, which crashes rustdoc-json.
While investigating this, It turns out somehow, some items are being documented twice. I'm not sure how this is happening but for now, we just make sure they were the same if they have the same id.
Zulip descussion
Bless script (Once this is more pollished I'll submit it)
r? @jyn514